Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c60b8f5439d64b3be7942f8b25d9152f043dae1d3460a121876e08e9c7d44633

Tx prefix hash: c4b085f9196889376c6c1d40f20e72bc29838b6ec22dc03ac1a763088e36a0f1
Tx public key: 6bec33efb471794f5a27211ff07fdcebbd9708eedc9ee841cb53e35346c44258
Timestamp: 1704575450 Timestamp [UCT]: 2024-01-06 21:10:50 Age [y:d:h:m:s]: 01:312:18:39:13
Block: 929660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482378 RingCT/type: yes/0
Extra: 016bec33efb471794f5a27211ff07fdcebbd9708eedc9ee841cb53e35346c442580211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0c5e4c5ef1e07afb2844c15e7c5b3fb54600d959eaec4778717daf65d4a9ca4 0.600000000000 1387536 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": 929670, "vin": [ { "gen": { "height": 929660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0c5e4c5ef1e07afb2844c15e7c5b3fb54600d959eaec4778717daf65d4a9ca4" } } ], "extra": [ 1, 107, 236, 51, 239, 180, 113, 121, 79, 90, 39, 33, 31, 240, 127, 220, 235, 189, 151, 8, 238, 220, 158, 232, 65, 203, 83, 227, 83, 70, 196, 66, 88, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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