Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896fd800628e824f39b34c9cf7a1aea0be1a901d60e13d6753ac3f55b0b6514c

Tx prefix hash: 7a4edace5a8ec54699523853ac613a3b3a8af72f5d87ec4f9149040fa63b5795
Tx public key: 5c53e83b6be5836a494bac20a8bdd3e0f33dd0b7b6ef2289470803b836a69bb0
Timestamp: 1730888737 Timestamp [UCT]: 2024-11-06 10:25:37 Age [y:d:h:m:s]: 00:158:21:24:40
Block: 1147737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113420 RingCT/type: yes/0
Extra: 015c53e83b6be5836a494bac20a8bdd3e0f33dd0b7b6ef2289470803b836a69bb00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 841a478254d31527c6020197882db2b5736c993ee4daf0716cdd92f8b39f925f 0.600000000000 1632438 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": 1147747, "vin": [ { "gen": { "height": 1147737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "841a478254d31527c6020197882db2b5736c993ee4daf0716cdd92f8b39f925f" } } ], "extra": [ 1, 92, 83, 232, 59, 107, 229, 131, 106, 73, 75, 172, 32, 168, 189, 211, 224, 243, 61, 208, 183, 182, 239, 34, 137, 71, 8, 3, 184, 54, 166, 155, 176, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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