Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61150763a8be1dca8b8f9a1be3fe2baa88937896031b1bb4a4a101b84a2961ab

Tx prefix hash: 0ae46820798e20dd59434a28a8a3fc5938e6a0e70c6694f24860062a977bca69
Tx public key: 9d4a718919aa89b057ea1ea90853968ea74f9cfa53d5917e40604ecb7924f059
Timestamp: 1730894647 Timestamp [UCT]: 2024-11-06 12:04:07 Age [y:d:h:m:s]: 00:181:10:50:46
Block: 1147788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129538 RingCT/type: yes/0
Extra: 019d4a718919aa89b057ea1ea90853968ea74f9cfa53d5917e40604ecb7924f0590211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e85e40021e56c1bd00369f3839fe01a0dba8f2f41976fda0d224ec559802dc8 0.600000000000 1632489 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": 1147798, "vin": [ { "gen": { "height": 1147788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e85e40021e56c1bd00369f3839fe01a0dba8f2f41976fda0d224ec559802dc8" } } ], "extra": [ 1, 157, 74, 113, 137, 25, 170, 137, 176, 87, 234, 30, 169, 8, 83, 150, 142, 167, 79, 156, 250, 83, 213, 145, 126, 64, 96, 78, 203, 121, 36, 240, 89, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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