Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e95222e19eb303558591e35d6c854ee41e4fc43ad29db61ab1b3a5f8211a11

Tx prefix hash: c066ac427625ee3b80fdac50052162451c0515e4c2241cd834de6fb1c0ef30a1
Tx public key: e42580848a6d32744d9cb8a6702bbd976a2b9df8ff231d76e089c696657747cb
Timestamp: 1731011782 Timestamp [UCT]: 2024-11-07 20:36:22 Age [y:d:h:m:s]: 00:156:11:07:54
Block: 1148762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111656 RingCT/type: yes/0
Extra: 01e42580848a6d32744d9cb8a6702bbd976a2b9df8ff231d76e089c696657747cb021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16ba901e3a71218978e0c6365a979bd803abf73fd35f305b11e1c34c0b159f35 0.600000000000 1633681 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": 1148772, "vin": [ { "gen": { "height": 1148762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16ba901e3a71218978e0c6365a979bd803abf73fd35f305b11e1c34c0b159f35" } } ], "extra": [ 1, 228, 37, 128, 132, 138, 109, 50, 116, 77, 156, 184, 166, 112, 43, 189, 151, 106, 43, 157, 248, 255, 35, 29, 118, 224, 137, 198, 150, 101, 119, 71, 203, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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