Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 189345fe1e2edd0df4b4482270eca087c386a9345b5dc38ef4bde69593d0468c

Tx prefix hash: 974892879581a20729ea8ab2b0da59ec9c3644dd5e7d2e308b13f1c39a6d47e8
Tx public key: f51ec745905d2c46a73148dcc1de059fdd3e1333ab1b4580849c327902e4c50f
Timestamp: 1681424120 Timestamp [UCT]: 2023-04-13 22:15:20 Age [y:d:h:m:s]: 01:316:16:33:07
Block: 737980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487580 RingCT/type: yes/0
Extra: 01f51ec745905d2c46a73148dcc1de059fdd3e1333ab1b4580849c327902e4c50f0211000000045029cbac000000000000000000

1 output(s) for total of 2.201740498000 dcy

stealth address amount amount idx
00: 88dae9d476d3be68b5535a74a74a42db3930d41f0a0a4bb18b4260cc5fe199c9 2.201740498000 1184611 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": 737990, "vin": [ { "gen": { "height": 737980 } } ], "vout": [ { "amount": 2201740498, "target": { "key": "88dae9d476d3be68b5535a74a74a42db3930d41f0a0a4bb18b4260cc5fe199c9" } } ], "extra": [ 1, 245, 30, 199, 69, 144, 93, 44, 70, 167, 49, 72, 220, 193, 222, 5, 159, 221, 62, 19, 51, 171, 27, 69, 128, 132, 156, 50, 121, 2, 228, 197, 15, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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