Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf06a556fb89ef5d6502c3aeab765d2c63ec8e1314ae678c3e0c6918a50c0417

Tx prefix hash: e2639da834a1c8e21908ef79715d3fbc07d17c2cebaa262a99f5480254f79699
Tx public key: 6954e395b9f0068928e9043b2b428b7857c634ba0b4de63cbe9e58a7b9a0fae5
Timestamp: 1699054425 Timestamp [UCT]: 2023-11-03 23:33:45 Age [y:d:h:m:s]: 02:011:10:42:34
Block: 884109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527771 RingCT/type: yes/0
Extra: 016954e395b9f0068928e9043b2b428b7857c634ba0b4de63cbe9e58a7b9a0fae5021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.722070959000 dcy

stealth address amount amount idx
00: 56f991a89e6ec04d629f3bf3fecce49b615e51c00316dca21b83f5d881ce72e0 0.722070959000 1339842 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": 884119, "vin": [ { "gen": { "height": 884109 } } ], "vout": [ { "amount": 722070959, "target": { "key": "56f991a89e6ec04d629f3bf3fecce49b615e51c00316dca21b83f5d881ce72e0" } } ], "extra": [ 1, 105, 84, 227, 149, 185, 240, 6, 137, 40, 233, 4, 59, 43, 66, 139, 120, 87, 198, 52, 186, 11, 77, 230, 60, 190, 158, 88, 167, 185, 160, 250, 229, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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