Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 166ca8e073f45294980c2fae2bca317b4757ecdd1bb97746ccb99e5bd521282a

Tx prefix hash: 1f3dc6daa5caf062aab57c30f60e93dab4bdeb9a6ae318bead299c12772914b9
Tx public key: e96edb554016f984d12ff847fb20f601b446e240d1fadbffc0b5d639dc356df4
Timestamp: 1696700255 Timestamp [UCT]: 2023-10-07 17:37:35 Age [y:d:h:m:s]: 01:109:13:06:45
Block: 864589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339525 RingCT/type: yes/0
Extra: 01e96edb554016f984d12ff847fb20f601b446e240d1fadbffc0b5d639dc356df4021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.838026535000 dcy

stealth address amount amount idx
00: fb1a6086950183c513514facca71c564d7c26268d55feab46382ef0f284d9ce9 0.838026535000 1319109 of 0

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": 864599, "vin": [ { "gen": { "height": 864589 } } ], "vout": [ { "amount": 838026535, "target": { "key": "fb1a6086950183c513514facca71c564d7c26268d55feab46382ef0f284d9ce9" } } ], "extra": [ 1, 233, 110, 219, 85, 64, 22, 249, 132, 209, 47, 248, 71, 251, 32, 246, 1, 180, 70, 226, 64, 209, 250, 219, 255, 192, 181, 214, 57, 220, 53, 109, 244, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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