Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2ccbb684b6c85ef7098d8946145344a3730bf6d7a5325b64991f8c081af45f

Tx prefix hash: 1fae56d042e2ffba2a89f7dabeebfad7dbfa35672d1f56a049e0e54e704e36c7
Tx public key: f58c11f09156379064ad938c1269b52488309616c8552dbff5fedfb53bb8d2d5
Timestamp: 1697313100 Timestamp [UCT]: 2023-10-14 19:51:40 Age [y:d:h:m:s]: 02:022:18:33:11
Block: 869675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535870 RingCT/type: yes/0
Extra: 01f58c11f09156379064ad938c1269b52488309616c8552dbff5fedfb53bb8d2d502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.806141206000 dcy

stealth address amount amount idx
00: 6956f4249d3dcf531eff76c355384d7c27f0d0810f627dc8e853a812d4263819 0.806141206000 1324526 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": 869685, "vin": [ { "gen": { "height": 869675 } } ], "vout": [ { "amount": 806141206, "target": { "key": "6956f4249d3dcf531eff76c355384d7c27f0d0810f627dc8e853a812d4263819" } } ], "extra": [ 1, 245, 140, 17, 240, 145, 86, 55, 144, 100, 173, 147, 140, 18, 105, 181, 36, 136, 48, 150, 22, 200, 85, 45, 191, 245, 254, 223, 181, 59, 184, 210, 213, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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