Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ccfd6516aa3d3bac26a25ca33c93085e3ba8c1ed22fa7ee8009f07b2404ebcc

Tx prefix hash: b936c18288e3d28f6ff8ff0a19ea0de3990d9f7d3deb04bbc389e96e6c5855f7
Tx public key: 0b841f300c768fde75510187210605a3f8e15d0f5b5b6124fecfa860afdecb14
Timestamp: 1731647498 Timestamp [UCT]: 2024-11-15 05:11:38 Age [y:d:h:m:s]: 00:008:16:38:18
Block: 1154019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6223 RingCT/type: yes/0
Extra: 010b841f300c768fde75510187210605a3f8e15d0f5b5b6124fecfa860afdecb1402110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 864df55e3f3e69495dfeb59e0841fc15a1dfe9550e50fb128d72b4ecd712b22f 0.600000000000 1639630 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": 1154029, "vin": [ { "gen": { "height": 1154019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "864df55e3f3e69495dfeb59e0841fc15a1dfe9550e50fb128d72b4ecd712b22f" } } ], "extra": [ 1, 11, 132, 31, 48, 12, 118, 143, 222, 117, 81, 1, 135, 33, 6, 5, 163, 248, 225, 93, 15, 91, 91, 97, 36, 254, 207, 168, 96, 175, 222, 203, 20, 2, 17, 0, 0, 0, 12, 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