Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8b63bc96dea763253431210a6588db4f872d1b8c4c74dfa28be091f2df7ba7

Tx prefix hash: f354881c023919f0469845e61ee1fa21544389ca1959aa1b8e0e55c5d30d722e
Tx public key: 23e67fd673c5bf78d21f667b5dfc60329a1660feb43298a5d2f3b09939434e0b
Timestamp: 1713226842 Timestamp [UCT]: 2024-04-16 00:20:42 Age [y:d:h:m:s]: 00:353:14:33:09
Block: 1001387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252814 RingCT/type: yes/0
Extra: 0123e67fd673c5bf78d21f667b5dfc60329a1660feb43298a5d2f3b09939434e0b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d27970af9248dc44e5e813413f11844565f88a30447e2ae3e1baa5dd14abffa 0.600000000000 1461891 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": 1001397, "vin": [ { "gen": { "height": 1001387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d27970af9248dc44e5e813413f11844565f88a30447e2ae3e1baa5dd14abffa" } } ], "extra": [ 1, 35, 230, 127, 214, 115, 197, 191, 120, 210, 31, 102, 123, 93, 252, 96, 50, 154, 22, 96, 254, 180, 50, 152, 165, 210, 243, 176, 153, 57, 67, 78, 11, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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