Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973b699b312d31dafb99ce67faa9555417fcd236a8e1eb580b7ebfb5c5e8e3ed

Tx prefix hash: 7cfb44778a26701ec8a603ce2ba7235c9cb4f5ee6c0129b8edf44888cccd7f87
Tx public key: f48e4d8490bb0ed547a78bee0a1e88009951511f226d19bcf6c0b884ed6bc6be
Timestamp: 1722874915 Timestamp [UCT]: 2024-08-05 16:21:55 Age [y:d:h:m:s]: 00:201:06:23:58
Block: 1081383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143709 RingCT/type: yes/0
Extra: 01f48e4d8490bb0ed547a78bee0a1e88009951511f226d19bcf6c0b884ed6bc6be02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca4893d700654208dc8f06d755c6e35842ce93fb30639fc530247b325dec45c4 0.600000000000 1555110 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": 1081393, "vin": [ { "gen": { "height": 1081383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca4893d700654208dc8f06d755c6e35842ce93fb30639fc530247b325dec45c4" } } ], "extra": [ 1, 244, 142, 77, 132, 144, 187, 14, 213, 71, 167, 139, 238, 10, 30, 136, 0, 153, 81, 81, 31, 34, 109, 25, 188, 246, 192, 184, 132, 237, 107, 198, 190, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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