Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ace55ce2b4c6e429c7ec0b781195fc6b876d233560fb32d37a3952e7cf79767

Tx prefix hash: 073437b4d833cc8eafde7cef88620186c781444af840fd4fb73a1536c41d3885
Tx public key: 102088f3df8a5309275b8e42e78f56a0e61c277c354bb3306467ea0c2399678d
Timestamp: 1732919990 Timestamp [UCT]: 2024-11-29 22:39:50 Age [y:d:h:m:s]: 00:027:01:10:37
Block: 1164568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19355 RingCT/type: yes/0
Extra: 01102088f3df8a5309275b8e42e78f56a0e61c277c354bb3306467ea0c2399678d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c3a52b2535426163e87ae27bed7ad652707e6fcbe0abf6c09222e1fc920be21 0.600000000000 1650241 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": 1164578, "vin": [ { "gen": { "height": 1164568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c3a52b2535426163e87ae27bed7ad652707e6fcbe0abf6c09222e1fc920be21" } } ], "extra": [ 1, 16, 32, 136, 243, 223, 138, 83, 9, 39, 91, 142, 66, 231, 143, 86, 160, 230, 28, 39, 124, 53, 75, 179, 48, 100, 103, 234, 12, 35, 153, 103, 141, 2, 17, 0, 0, 0, 6, 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