Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0dfe77c7c3e45a1773cb1cb0461392a4a157e2f58999c26e440e891ef2d24dc

Tx prefix hash: 10fdc2535eb546fb9daff969c1fc33cb7cf8517111935f2ae6414b23c54d3927
Tx public key: 9ec141f12dc6b0f81bec6ecf15f7c10184278746ab5513f904bcfd4601b292e8
Timestamp: 1734760994 Timestamp [UCT]: 2024-12-21 06:03:14 Age [y:d:h:m:s]: 00:015:00:00:03
Block: 1179844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10708 RingCT/type: yes/0
Extra: 019ec141f12dc6b0f81bec6ecf15f7c10184278746ab5513f904bcfd4601b292e80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c196173b08fc7b7b7cd28b9d1ced1dc42ff17a284442d744af80f1d2e72df4c 0.600000000000 1666243 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": 1179854, "vin": [ { "gen": { "height": 1179844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c196173b08fc7b7b7cd28b9d1ced1dc42ff17a284442d744af80f1d2e72df4c" } } ], "extra": [ 1, 158, 193, 65, 241, 45, 198, 176, 248, 27, 236, 110, 207, 21, 247, 193, 1, 132, 39, 135, 70, 171, 85, 19, 249, 4, 188, 253, 70, 1, 178, 146, 232, 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