Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fff286063e8c383734a3200508cb2721ba73b5d288107fd8572d7542aa16cb1

Tx prefix hash: 05784431a47a7415bafa9e301766fd478af76f55f012527e1c00ed8cd6ec17c8
Tx public key: 031a16cfd4da1d29b699dca20bedc80a7dfe7cf65812ca29e1b81a728e8696cb
Timestamp: 1704834291 Timestamp [UCT]: 2024-01-09 21:04:51 Age [y:d:h:m:s]: 01:157:11:01:49
Block: 931812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373599 RingCT/type: yes/0
Extra: 01031a16cfd4da1d29b699dca20bedc80a7dfe7cf65812ca29e1b81a728e8696cb0211000000029da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ed1aa17dcb68597701297c15bfe964759bc0b79f2c9e6e13c10b9c038e54cb9 0.600000000000 1389716 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": 931822, "vin": [ { "gen": { "height": 931812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ed1aa17dcb68597701297c15bfe964759bc0b79f2c9e6e13c10b9c038e54cb9" } } ], "extra": [ 1, 3, 26, 22, 207, 212, 218, 29, 41, 182, 153, 220, 162, 11, 237, 200, 10, 125, 254, 124, 246, 88, 18, 202, 41, 225, 184, 26, 114, 142, 134, 150, 203, 2, 17, 0, 0, 0, 2, 157, 168, 225, 52, 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