Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39f40110971df306bf8252b35d4c52cea75a3f30d8139195b2b17e092989091c

Tx prefix hash: 7913a33234343444472bf519a107533b5c4578cb3c092a58eb1acd7ada1e851d
Tx public key: 2eff1284fa502d3ebcdd2266aa607f3bfe728c51e9597b9f0eb4f0620a519a38
Timestamp: 1675093955 Timestamp [UCT]: 2023-01-30 15:52:35 Age [y:d:h:m:s]: 02:101:16:29:59
Block: 686134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594341 RingCT/type: yes/0
Extra: 012eff1284fa502d3ebcdd2266aa607f3bfe728c51e9597b9f0eb4f0620a519a380211000000045029cbac000000000000000000

1 output(s) for total of 3.270040743000 dcy

stealth address amount amount idx
00: bfff2007c9a960caf6b6c6af026e6fa59cda41bb0000c5ea55c3ec32545c53d1 3.270040743000 1128599 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": 686144, "vin": [ { "gen": { "height": 686134 } } ], "vout": [ { "amount": 3270040743, "target": { "key": "bfff2007c9a960caf6b6c6af026e6fa59cda41bb0000c5ea55c3ec32545c53d1" } } ], "extra": [ 1, 46, 255, 18, 132, 250, 80, 45, 62, 188, 221, 34, 102, 170, 96, 127, 59, 254, 114, 140, 81, 233, 89, 123, 159, 14, 180, 240, 98, 10, 81, 154, 56, 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