Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c10cd06b548a32c2f118894692d1175271ce81aee1ccdf64ca3a834e24bad85d

Tx prefix hash: 0ffae9e7271cad47dbb727f71518374164058b6eecf83da92ef0cce983711bb5
Tx public key: c32fc4c42f7244d2b3d4ced9b9382e65bf4c5beb2332e02bc34d72c6f0c6815b
Timestamp: 1706427036 Timestamp [UCT]: 2024-01-28 07:30:36 Age [y:d:h:m:s]: 01:281:05:24:05
Block: 945006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459789 RingCT/type: yes/0
Extra: 01c32fc4c42f7244d2b3d4ced9b9382e65bf4c5beb2332e02bc34d72c6f0c6815b02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8355ca2c64e1123b73a343086a5d2ecc8aa8024f66b878e8fb47a3b66f38988e 0.600000000000 1403314 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": 945016, "vin": [ { "gen": { "height": 945006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8355ca2c64e1123b73a343086a5d2ecc8aa8024f66b878e8fb47a3b66f38988e" } } ], "extra": [ 1, 195, 47, 196, 196, 47, 114, 68, 210, 179, 212, 206, 217, 185, 56, 46, 101, 191, 76, 91, 235, 35, 50, 224, 43, 195, 77, 114, 198, 240, 198, 129, 91, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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