Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 921c0a404f246ce627d8588bf45307c73bf6378d89677b572740d8e724cd1c52

Tx prefix hash: 677e774c41446dd03de7b0e04804614f3c1c6e3d01937303e352b570bba2e14e
Tx public key: 6c20f8c52f54e78f94d24d83e02918f911d2d6d211f58c61cd51d3ad67df1522
Timestamp: 1735728136 Timestamp [UCT]: 2025-01-01 10:42:16 Age [y:d:h:m:s]: 00:168:06:27:59
Block: 1187817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119975 RingCT/type: yes/0
Extra: 016c20f8c52f54e78f94d24d83e02918f911d2d6d211f58c61cd51d3ad67df152202110000001d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d3276f24159df69da7f30de4b239075f0e4916c3117a9c321d2c2c5d13c6342 0.600000000000 1674314 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": 1187827, "vin": [ { "gen": { "height": 1187817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d3276f24159df69da7f30de4b239075f0e4916c3117a9c321d2c2c5d13c6342" } } ], "extra": [ 1, 108, 32, 248, 197, 47, 84, 231, 143, 148, 210, 77, 131, 224, 41, 24, 249, 17, 210, 214, 210, 17, 245, 140, 97, 205, 81, 211, 173, 103, 223, 21, 34, 2, 17, 0, 0, 0, 29, 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