Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c578e10530ce58a3061a6c25f6a586d2fadb0076c3030d6e3c3f361eac2e76

Tx prefix hash: e64cf35065d5dc987af17cea44b5f230f4e014e54b35ef4fa9d6e9376e908ac7
Tx public key: 64a0e86ccfcbf588c72b4f9c4f4480d5e69e5e31a4e659c96529511505dee131
Timestamp: 1710191945 Timestamp [UCT]: 2024-03-11 21:19:05 Age [y:d:h:m:s]: 01:265:05:53:40
Block: 976253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448303 RingCT/type: yes/0
Extra: 0164a0e86ccfcbf588c72b4f9c4f4480d5e69e5e31a4e659c96529511505dee1310211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6f1ecded521c664910be005800419be04ae82981b2502c31b8591c166b8a6e 0.600000000000 1436244 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": 976263, "vin": [ { "gen": { "height": 976253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6f1ecded521c664910be005800419be04ae82981b2502c31b8591c166b8a6e" } } ], "extra": [ 1, 100, 160, 232, 108, 207, 203, 245, 136, 199, 43, 79, 156, 79, 68, 128, 213, 230, 158, 94, 49, 164, 230, 89, 201, 101, 41, 81, 21, 5, 222, 225, 49, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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