Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 53c17da4fd1ec30355d036f6b8303430142b6e493bcccddf44e13e743dcae764

Tx prefix hash: 34e7b8891ae883ac7be711e63cbb5ec1ea9fd441e4597c5ac93014c226c5025a
Tx public key: 3b331b7f633bae30bb77a99524c5e964959696b8a4b3c6457a2120d7386e13db
Timestamp: 1734914115 Timestamp [UCT]: 2024-12-23 00:35:15 Age [y:d:h:m:s]: 00:319:16:21:15
Block: 1181116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225948 RingCT/type: yes/0
Extra: 013b331b7f633bae30bb77a99524c5e964959696b8a4b3c6457a2120d7386e13db0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eaff0b94d149eaf8fa44a104db844b0db9b6159e98478a6fabaae006403b573 0.600000000000 1667531 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1181126, "vin": [ { "gen": { "height": 1181116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eaff0b94d149eaf8fa44a104db844b0db9b6159e98478a6fabaae006403b573" } } ], "extra": [ 1, 59, 51, 27, 127, 99, 59, 174, 48, 187, 119, 169, 149, 36, 197, 233, 100, 149, 150, 150, 184, 164, 179, 198, 69, 122, 33, 32, 215, 56, 110, 19, 219, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8