Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d7be19cbdc17a9d394acd5d5470fd6f4b8c2d6176d466f618bb1eb111ed2e3

Tx prefix hash: b21d5e37186dc5d517490444b2c05e672c1bddade0072e37980d422e1a14db55
Tx public key: f0092f0df6d3c5ba07611154aa4b742dc0bd725c1f000524d2be6ee5c097917c
Timestamp: 1705548485 Timestamp [UCT]: 2024-01-18 03:28:05 Age [y:d:h:m:s]: 01:295:07:02:57
Block: 937719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469868 RingCT/type: yes/0
Extra: 01f0092f0df6d3c5ba07611154aa4b742dc0bd725c1f000524d2be6ee5c097917c02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d45dac352349bf575f98a89396b667b840c95730d54ec306d1ca32ae47c3294b 0.600000000000 1395781 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": 937729, "vin": [ { "gen": { "height": 937719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d45dac352349bf575f98a89396b667b840c95730d54ec306d1ca32ae47c3294b" } } ], "extra": [ 1, 240, 9, 47, 13, 246, 211, 197, 186, 7, 97, 17, 84, 170, 75, 116, 45, 192, 189, 114, 92, 31, 0, 5, 36, 210, 190, 110, 229, 192, 151, 145, 124, 2, 17, 0, 0, 0, 10, 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