Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8884716b0680c77b572e08d6ebc41bbfb440d4a986ca5118656857e139777fea

Tx prefix hash: 5f2e6fd594f0a447fc262c737196a65a8ce5161e82ce98379577e7406b97ca1b
Tx public key: 08c8bdcfcce3de19109107eb5f36f5f18960411494d2b04cf5b7e37252baa7b9
Timestamp: 1699662826 Timestamp [UCT]: 2023-11-11 00:33:46 Age [y:d:h:m:s]: 01:192:09:25:48
Block: 888960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398719 RingCT/type: yes/0
Extra: 0108c8bdcfcce3de19109107eb5f36f5f18960411494d2b04cf5b7e37252baa7b9021100000003faf35c9c000000000000000000

1 output(s) for total of 0.695835361000 dcy

stealth address amount amount idx
00: a12b3f5e8ec2db327f4ba13187dd9c0fa0f9f5cabfb6db1f724a91256159a214 0.695835361000 1344929 of 0

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": 888970, "vin": [ { "gen": { "height": 888960 } } ], "vout": [ { "amount": 695835361, "target": { "key": "a12b3f5e8ec2db327f4ba13187dd9c0fa0f9f5cabfb6db1f724a91256159a214" } } ], "extra": [ 1, 8, 200, 189, 207, 204, 227, 222, 25, 16, 145, 7, 235, 95, 54, 245, 241, 137, 96, 65, 20, 148, 210, 176, 76, 245, 183, 227, 114, 82, 186, 167, 185, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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