Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 878708940e6dca966f9c9b880c33a10a6b49d47ce6a0bc8b8b275508f9769ab0

Tx prefix hash: 76eaa7d81f346bc072bba4829b5cf9f0e9964a4f40a5e9c990e88bf8043030bd
Tx public key: 04aa77d77db2d15cf34c29883ce77e9cb8f142b8759988057248a8a58c10df32
Timestamp: 1704759747 Timestamp [UCT]: 2024-01-09 00:22:27 Age [y:d:h:m:s]: 01:086:09:40:25
Block: 931187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322870 RingCT/type: yes/0
Extra: 0104aa77d77db2d15cf34c29883ce77e9cb8f142b8759988057248a8a58c10df3202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c7bbce57e58033b847a218c09e19672402e1419420ef67f217c52532765a7b 0.600000000000 1389081 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": 931197, "vin": [ { "gen": { "height": 931187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c7bbce57e58033b847a218c09e19672402e1419420ef67f217c52532765a7b" } } ], "extra": [ 1, 4, 170, 119, 215, 125, 178, 209, 92, 243, 76, 41, 136, 60, 231, 126, 156, 184, 241, 66, 184, 117, 153, 136, 5, 114, 72, 168, 165, 140, 16, 223, 50, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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