Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5b39b5697d996bfc9baf2b6000d0143985b8a2a37e14d771e1229b66fd0d34

Tx prefix hash: c4bd3891cfaa04c54f971ec039d8a9591b91629b1b2b5cefd47150a8eb44449a
Tx public key: 1027410d91df770298b2fd1d7c9fb89ce0c006eedf70ca10cf289d25d8310999
Timestamp: 1681681751 Timestamp [UCT]: 2023-04-16 21:49:11 Age [y:d:h:m:s]: 01:271:02:15:40
Block: 740115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455251 RingCT/type: yes/0
Extra: 011027410d91df770298b2fd1d7c9fb89ce0c006eedf70ca10cf289d25d83109990211000000045029cbac000000000000000000

1 output(s) for total of 2.166167254000 dcy

stealth address amount amount idx
00: d170ea12560e040dae7e396a9297d7875cef5e4a1d7bb4a27a2bcc831df1fde3 2.166167254000 1186996 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": 740125, "vin": [ { "gen": { "height": 740115 } } ], "vout": [ { "amount": 2166167254, "target": { "key": "d170ea12560e040dae7e396a9297d7875cef5e4a1d7bb4a27a2bcc831df1fde3" } } ], "extra": [ 1, 16, 39, 65, 13, 145, 223, 119, 2, 152, 178, 253, 29, 124, 159, 184, 156, 224, 192, 6, 238, 223, 112, 202, 16, 207, 40, 157, 37, 216, 49, 9, 153, 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