Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2be45fe19cfab84dac7b14d5225b97a906190c4a8010d439b1ab1aca4078769b

Tx prefix hash: 55b1c6a2d37b37ce3edbac585e0ae5143bf311fbaa7f34b1cbc17ecba60ed3c8
Tx public key: f1df94e117dd31216832eb207494d5a126a3be932f05a8e38bf9a0c311810b76
Timestamp: 1673202825 Timestamp [UCT]: 2023-01-08 18:33:45 Age [y:d:h:m:s]: 02:142:10:07:24
Block: 670432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623531 RingCT/type: yes/0
Extra: 01f1df94e117dd31216832eb207494d5a126a3be932f05a8e38bf9a0c311810b7602110000000152542ceb000000000000000000

1 output(s) for total of 3.686213039000 dcy

stealth address amount amount idx
00: 392f710cf98970ddad4fb7ac2f498f08888a71db53af8c21d364043763158943 3.686213039000 1111837 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": 670442, "vin": [ { "gen": { "height": 670432 } } ], "vout": [ { "amount": 3686213039, "target": { "key": "392f710cf98970ddad4fb7ac2f498f08888a71db53af8c21d364043763158943" } } ], "extra": [ 1, 241, 223, 148, 225, 23, 221, 49, 33, 104, 50, 235, 32, 116, 148, 213, 161, 38, 163, 190, 147, 47, 5, 168, 227, 139, 249, 160, 195, 17, 129, 11, 118, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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