Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2701317167754fcbbd5ae16dd36de57784d3e2b141fa3bb84aba434f1e089005

Tx prefix hash: af09d9cf28a5804c464b206ebb388b570539fa5c43f7f268a62f50b4737463ed
Tx public key: f53c8cb2e06a3d7bbe898b09d6c258edc5c43a65c9e518c117ca709199cb1cb0
Timestamp: 1708185549 Timestamp [UCT]: 2024-02-17 15:59:09 Age [y:d:h:m:s]: 01:122:00:01:08
Block: 959609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348152 RingCT/type: yes/0
Extra: 01f53c8cb2e06a3d7bbe898b09d6c258edc5c43a65c9e518c117ca709199cb1cb00211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30f1f226cd3e05ac1ffbd91af0340dccb98547a553aa267c8eb012e6bf4d494b 0.600000000000 1419160 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": 959619, "vin": [ { "gen": { "height": 959609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30f1f226cd3e05ac1ffbd91af0340dccb98547a553aa267c8eb012e6bf4d494b" } } ], "extra": [ 1, 245, 60, 140, 178, 224, 106, 61, 123, 190, 137, 139, 9, 214, 194, 88, 237, 197, 196, 58, 101, 201, 229, 24, 193, 23, 202, 112, 145, 153, 203, 28, 176, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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