Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aae11ac30aacbb0482ec8ee0e938f458b7782679418b08b7fad00e1df25e473b

Tx prefix hash: e938ae1d7546440a54dc738c9e1e2dc9df437917639f6b7127c69bfe54724123
Tx public key: 84295700f8f3a98777f2540d92a0f0e96d45ae6c6d3c3faadda22c3ac5dbc823
Timestamp: 1694204289 Timestamp [UCT]: 2023-09-08 20:18:09 Age [y:d:h:m:s]: 01:280:14:56:21
Block: 843884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461611 RingCT/type: yes/0
Extra: 0184295700f8f3a98777f2540d92a0f0e96d45ae6c6d3c3faadda22c3ac5dbc82302110000000733af99f4000000000000000000

1 output(s) for total of 0.981436173000 dcy

stealth address amount amount idx
00: 02ac30aa05728aa2a2edb91ae60e5d585ac38eceec92d210210f0441aff638d8 0.981436173000 1297158 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": 843894, "vin": [ { "gen": { "height": 843884 } } ], "vout": [ { "amount": 981436173, "target": { "key": "02ac30aa05728aa2a2edb91ae60e5d585ac38eceec92d210210f0441aff638d8" } } ], "extra": [ 1, 132, 41, 87, 0, 248, 243, 169, 135, 119, 242, 84, 13, 146, 160, 240, 233, 109, 69, 174, 108, 109, 60, 63, 170, 221, 162, 44, 58, 197, 219, 200, 35, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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