Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb409ffe00ceb45638de68d809f4df1a5f4403eba0d171d019b2440958cc0732

Tx prefix hash: e283920d029c23918bc8351fd73a9304e15bcfce98aeffc254d77e35caab7877
Tx public key: 3d3212071d71a1ebc1204507fe3db975b66a31c1db8ccae31bd31e627774a5e3
Timestamp: 1723553911 Timestamp [UCT]: 2024-08-13 12:58:31 Age [y:d:h:m:s]: 00:215:23:23:50
Block: 1087019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154246 RingCT/type: yes/0
Extra: 013d3212071d71a1ebc1204507fe3db975b66a31c1db8ccae31bd31e627774a5e302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d8ea94e8d9246863cf69b2cdf0b7ae19c9ffa7585757c9fd60591a2cfc7b043 0.600000000000 1561620 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": 1087029, "vin": [ { "gen": { "height": 1087019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d8ea94e8d9246863cf69b2cdf0b7ae19c9ffa7585757c9fd60591a2cfc7b043" } } ], "extra": [ 1, 61, 50, 18, 7, 29, 113, 161, 235, 193, 32, 69, 7, 254, 61, 185, 117, 182, 106, 49, 193, 219, 140, 202, 227, 27, 211, 30, 98, 119, 116, 165, 227, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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