Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8f15a8308504aaee49e6e2ef1d947f962d98b06f9aa410db0a97cad06917d03

Tx prefix hash: c38eecd220af81c90315aa21b3e9dc1fb0e5e22c2ce1cced2bb049dcb1622a5f
Tx public key: 3d27e478b1351cdb49c967a95be53a54fba2d2ae71e0d0c4899ce0d20179fe46
Timestamp: 1736833747 Timestamp [UCT]: 2025-01-14 05:49:07 Age [y:d:h:m:s]: 00:336:06:59:59
Block: 1196974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237886 RingCT/type: yes/0
Extra: 013d27e478b1351cdb49c967a95be53a54fba2d2ae71e0d0c4899ce0d20179fe460211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bc896da22e21f04913f7cd2e969e2f2b70b43b63091290a912ec7c8d1315f1c 0.600000000000 1683579 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": 1196984, "vin": [ { "gen": { "height": 1196974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bc896da22e21f04913f7cd2e969e2f2b70b43b63091290a912ec7c8d1315f1c" } } ], "extra": [ 1, 61, 39, 228, 120, 177, 53, 28, 219, 73, 201, 103, 169, 91, 229, 58, 84, 251, 162, 210, 174, 113, 224, 208, 196, 137, 156, 224, 210, 1, 121, 254, 70, 2, 17, 0, 0, 0, 2, 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