Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3848cb13733fdab4d60aded9333e4388c3a5c8b678585dc1e7eccfed3cd093d

Tx prefix hash: ac7c2629090a0e1a8cf391642d16d3923060e4a42f7e2d4d8fcc92b2a3798795
Tx public key: 3b783d2f2dbb0d090c204c83e1989bfd0f6074e9d0d3a786a71a49860ff47766
Timestamp: 1721439483 Timestamp [UCT]: 2024-07-20 01:38:03 Age [y:d:h:m:s]: 00:174:10:29:21
Block: 1069528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124770 RingCT/type: yes/0
Extra: 013b783d2f2dbb0d090c204c83e1989bfd0f6074e9d0d3a786a71a49860ff47766021100000001162613aa000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 4f1480214c5bf4425c40e0f573eeff134d313cc8a9420a1d24e516fede3f8575 0.615600000000 1540977 of 0

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": 1069538, "vin": [ { "gen": { "height": 1069528 } } ], "vout": [ { "amount": 615600000, "target": { "key": "4f1480214c5bf4425c40e0f573eeff134d313cc8a9420a1d24e516fede3f8575" } } ], "extra": [ 1, 59, 120, 61, 47, 45, 187, 13, 9, 12, 32, 76, 131, 225, 152, 155, 253, 15, 96, 116, 233, 208, 211, 167, 134, 167, 26, 73, 134, 15, 244, 119, 102, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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