Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1ccce0485523bcd2ac40b9a27243ab129772b6fc1d27f1f6fa05cb33863507

Tx prefix hash: 616559de38a26237c1612ad0a625ed45bc2a3ab7b58c40a20078b6769b2da691
Tx public key: 9853d9d249f9a43d6aea8c73141b31b626e0176e50f5cf884c627572b75503a9
Timestamp: 1712154733 Timestamp [UCT]: 2024-04-03 14:32:13 Age [y:d:h:m:s]: 00:019:05:28:38
Block: 992494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13798 RingCT/type: yes/0
Extra: 019853d9d249f9a43d6aea8c73141b31b626e0176e50f5cf884c627572b75503a90211000000013f82f9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3703adf3a768f12cea2e143bb05de5e94e9afb6937fbf7d5ff31388b4c024184 0.600000000000 1452836 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": 992504, "vin": [ { "gen": { "height": 992494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3703adf3a768f12cea2e143bb05de5e94e9afb6937fbf7d5ff31388b4c024184" } } ], "extra": [ 1, 152, 83, 217, 210, 73, 249, 164, 61, 106, 234, 140, 115, 20, 27, 49, 182, 38, 224, 23, 110, 80, 245, 207, 136, 76, 98, 117, 114, 183, 85, 3, 169, 2, 17, 0, 0, 0, 1, 63, 130, 249, 251, 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