Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c0a903631f7b36f16fc4ad8de08048b0545f40a509618863ada5cd16ae49bda

Tx prefix hash: 50217dd5a9e77d1527be4ac253d9771fbf877638beb166e6bea6aa5db3f6de3d
Tx public key: 6736d93963cf081328b9f5cbc58934b04a32637367c5b230f5ec6a4266812eb9
Timestamp: 1734996098 Timestamp [UCT]: 2024-12-23 23:21:38 Age [y:d:h:m:s]: 00:088:16:41:50
Block: 1181778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63165 RingCT/type: yes/0
Extra: 016736d93963cf081328b9f5cbc58934b04a32637367c5b230f5ec6a4266812eb9021100000004d4a401e0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2fcb66e52301ad2dd6d70d0916163eecbbd3ea4f3ee92e5fbbb8ff1a630b174 0.600000000000 1668203 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": 1181788, "vin": [ { "gen": { "height": 1181778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2fcb66e52301ad2dd6d70d0916163eecbbd3ea4f3ee92e5fbbb8ff1a630b174" } } ], "extra": [ 1, 103, 54, 217, 57, 99, 207, 8, 19, 40, 185, 245, 203, 197, 137, 52, 176, 74, 50, 99, 115, 103, 197, 178, 48, 245, 236, 106, 66, 102, 129, 46, 185, 2, 17, 0, 0, 0, 4, 212, 164, 1, 224, 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