Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14718dd0658dfe72401428e7b225402c14d90fae2b809b7609a35033b28bba50

Tx prefix hash: e9b853e677087760200e7fe2e53694f48d9ce1eb51f8546a7b31c72973bae7cd
Tx public key: f2f4474a6ffee5da30df8afb5394be8f6063b44715d7c3acb25d558e8836a81d
Timestamp: 1732331998 Timestamp [UCT]: 2024-11-23 03:19:58 Age [y:d:h:m:s]: 00:001:03:19:43
Block: 1159695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 814 RingCT/type: yes/0
Extra: 01f2f4474a6ffee5da30df8afb5394be8f6063b44715d7c3acb25d558e8836a81d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dde2288a19c81fb534aebc7f8b5bfa79ea549d1ee399fa7a6827619d177d4b3 0.600000000000 1645334 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": 1159705, "vin": [ { "gen": { "height": 1159695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dde2288a19c81fb534aebc7f8b5bfa79ea549d1ee399fa7a6827619d177d4b3" } } ], "extra": [ 1, 242, 244, 71, 74, 111, 254, 229, 218, 48, 223, 138, 251, 83, 148, 190, 143, 96, 99, 180, 71, 21, 215, 195, 172, 178, 93, 85, 142, 136, 54, 168, 29, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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