Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e1c84dfeee98cb9b46fb8feaf4bb9389833b2570127b929137c7872afd346d0

Tx prefix hash: 67715599d243e18311ad44fa0daecc8ca96920617b3ace10d039f0f6f61ea865
Tx public key: 52c08d9df32ccd90714109e6f1c20f530825206f8c82ecb5a916e16f017e17b4
Timestamp: 1732265659 Timestamp [UCT]: 2024-11-22 08:54:19 Age [y:d:h:m:s]: 00:001:21:10:47
Block: 1159147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1344 RingCT/type: yes/0
Extra: 0152c08d9df32ccd90714109e6f1c20f530825206f8c82ecb5a916e16f017e17b4021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 843bcbd040c735e94e3a6e86f346242f8a10193a16fa56e0c319778099a35555 0.600000000000 1644778 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": 1159157, "vin": [ { "gen": { "height": 1159147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "843bcbd040c735e94e3a6e86f346242f8a10193a16fa56e0c319778099a35555" } } ], "extra": [ 1, 82, 192, 141, 157, 243, 44, 205, 144, 113, 65, 9, 230, 241, 194, 15, 83, 8, 37, 32, 111, 140, 130, 236, 181, 169, 22, 225, 111, 1, 126, 23, 180, 2, 17, 0, 0, 0, 5, 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