Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52d018f645e663891cae09fd20dce60643291b534f47ff53dfc2cc68c60bdb3

Tx prefix hash: d3c3b6f33b24e1bcef28992708526103154b15649114ee5fce89b91c35261a8e
Tx public key: c6b72d8c64cec783db7bee2a4b52fadb87e071a09f0edf654813fd4fe6b0b0d4
Timestamp: 1705025596 Timestamp [UCT]: 2024-01-12 02:13:16 Age [y:d:h:m:s]: 01:325:17:50:16
Block: 933392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491670 RingCT/type: yes/0
Extra: 01c6b72d8c64cec783db7bee2a4b52fadb87e071a09f0edf654813fd4fe6b0b0d40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59fe30d01a9ed434c9cf53488f6aae0a427798aab74146274958495748e232fc 0.600000000000 1391354 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": 933402, "vin": [ { "gen": { "height": 933392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59fe30d01a9ed434c9cf53488f6aae0a427798aab74146274958495748e232fc" } } ], "extra": [ 1, 198, 183, 45, 140, 100, 206, 199, 131, 219, 123, 238, 42, 75, 82, 250, 219, 135, 224, 113, 160, 159, 14, 223, 101, 72, 19, 253, 79, 230, 176, 176, 212, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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