Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33ffca43c3f137eeece08de5063f9b7b49af03b0d26e1cb4d029854b847e462

Tx prefix hash: 2fbe6c66f5011c505fb997c02da269f54dadd17b60c4c3a98a1e791213079b23
Tx public key: 6c3b01f5190315296da4b00c6581dea1b3381213479919929a4c4082a683a71e
Timestamp: 1715109205 Timestamp [UCT]: 2024-05-07 19:13:25 Age [y:d:h:m:s]: 00:238:20:08:49
Block: 1017013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170948 RingCT/type: yes/0
Extra: 016c3b01f5190315296da4b00c6581dea1b3381213479919929a4c4082a683a71e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2301e4c9114d9ac6fcbcaa2b24894eb9bfa89d4a79d18e55d88d04ecd392959 0.600000000000 1480762 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": 1017023, "vin": [ { "gen": { "height": 1017013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2301e4c9114d9ac6fcbcaa2b24894eb9bfa89d4a79d18e55d88d04ecd392959" } } ], "extra": [ 1, 108, 59, 1, 245, 25, 3, 21, 41, 109, 164, 176, 12, 101, 129, 222, 161, 179, 56, 18, 19, 71, 153, 25, 146, 154, 76, 64, 130, 166, 131, 167, 30, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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