Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c5a6ddb671068d6f35ab3ad14b3e76e78ad7605a05926c11fb710d7d9519473

Tx prefix hash: d565793b8d5c77e8f0a056f1fdc5459687cda42ee510381c96ab01354c4b5ad0
Tx public key: 0a8aabf9d0e3a8d8c4385c5cfba1c49152cf15f0f3807495f969ac4017f31f5d
Timestamp: 1722134339 Timestamp [UCT]: 2024-07-28 02:38:59 Age [y:d:h:m:s]: 00:247:02:07:16
Block: 1075249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176499 RingCT/type: yes/0
Extra: 010a8aabf9d0e3a8d8c4385c5cfba1c49152cf15f0f3807495f969ac4017f31f5d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1a91c0dd8498dac9f83c528e29d94a77675dcf6a53de28a81f86eac225c415d 0.600000000000 1547774 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": 1075259, "vin": [ { "gen": { "height": 1075249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1a91c0dd8498dac9f83c528e29d94a77675dcf6a53de28a81f86eac225c415d" } } ], "extra": [ 1, 10, 138, 171, 249, 208, 227, 168, 216, 196, 56, 92, 92, 251, 161, 196, 145, 82, 207, 21, 240, 243, 128, 116, 149, 249, 105, 172, 64, 23, 243, 31, 93, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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