Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09642b2f511f420b8dc519331bf2c4c4c32f14823c25da90a369e1c15bad728c

Tx prefix hash: d1a6e596dbd70a456e690a411cee7b4917aee8679adce2f708dfd0da657e0eef
Tx public key: 8aa3e435986015f85d9154bf3c8f5bfecf67c3342d97b6711207198344d9a37f
Timestamp: 1704530057 Timestamp [UCT]: 2024-01-06 08:34:17 Age [y:d:h:m:s]: 01:083:05:57:12
Block: 929278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320614 RingCT/type: yes/0
Extra: 018aa3e435986015f85d9154bf3c8f5bfecf67c3342d97b6711207198344d9a37f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7951aa3e39362c93dd3184d8302bb1ac1dcf7b29f86e42d1cb7249b939722f7 0.600000000000 1387150 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": 929288, "vin": [ { "gen": { "height": 929278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7951aa3e39362c93dd3184d8302bb1ac1dcf7b29f86e42d1cb7249b939722f7" } } ], "extra": [ 1, 138, 163, 228, 53, 152, 96, 21, 248, 93, 145, 84, 191, 60, 143, 91, 254, 207, 103, 195, 52, 45, 151, 182, 113, 18, 7, 25, 131, 68, 217, 163, 127, 2, 17, 0, 0, 0, 1, 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