Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c53efc1b85378d48e1b3115a6c0a4273180b7548e56b3dadd0b0c32eb28ada6e

Tx prefix hash: 6a12d8b4d5546bc51d13f86bba362e01b13e5f4b195e9b5f5151aeca02233e81
Tx public key: ee6830cc200a978f498c359d2a3e9738b3b473a285b515f9887d13e100e0e65d
Timestamp: 1737720170 Timestamp [UCT]: 2025-01-24 12:02:50 Age [y:d:h:m:s]: 00:257:21:26:42
Block: 1204273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181800 RingCT/type: yes/0
Extra: 01ee6830cc200a978f498c359d2a3e9738b3b473a285b515f9887d13e100e0e65d0211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8777e0b2ed8744e89138ed17620de5c09235f5dd9988ceefc549c8f6b6e23d3d 0.600000000000 1690958 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": 1204283, "vin": [ { "gen": { "height": 1204273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8777e0b2ed8744e89138ed17620de5c09235f5dd9988ceefc549c8f6b6e23d3d" } } ], "extra": [ 1, 238, 104, 48, 204, 32, 10, 151, 143, 73, 140, 53, 157, 42, 62, 151, 56, 179, 180, 115, 162, 133, 181, 21, 249, 136, 125, 19, 225, 0, 224, 230, 93, 2, 17, 0, 0, 0, 16, 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