Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f79ee5b05533c7e85360c855475c594e053bddf468cafdcd6fc2b22c9c36e0fa

Tx prefix hash: dd0476ed2976d27f6708b1908d6e3b33a6879240e868527b53911f6fb9e2d090
Tx public key: d796cae3c72e50c00e1939c2b6290c40cb32687e43ca0f4e79022c0d3df790fc
Timestamp: 1714249901 Timestamp [UCT]: 2024-04-27 20:31:41 Age [y:d:h:m:s]: 00:256:10:53:31
Block: 1009885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183558 RingCT/type: yes/0
Extra: 01d796cae3c72e50c00e1939c2b6290c40cb32687e43ca0f4e79022c0d3df790fc0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2bf060091dd5dbbb815834751cb8f61214af059eded61498e75a42c391c47a5 0.600000000000 1471681 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": 1009895, "vin": [ { "gen": { "height": 1009885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2bf060091dd5dbbb815834751cb8f61214af059eded61498e75a42c391c47a5" } } ], "extra": [ 1, 215, 150, 202, 227, 199, 46, 80, 192, 14, 25, 57, 194, 182, 41, 12, 64, 203, 50, 104, 126, 67, 202, 15, 78, 121, 2, 44, 13, 61, 247, 144, 252, 2, 17, 0, 0, 0, 4, 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