Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd43617285c96b6fc6656c089b6574b315e20ddc3691225b45c0983a3dd2853a

Tx prefix hash: d072e0bbbd0877b872215fd5d2b140bb103b64a728f4029caf766e6ad7b476d1
Tx public key: 197aff1c0c3ba4fe06d4b8af06e85293b27affe7788fb09b437c5a20d2551fc2
Timestamp: 1735453098 Timestamp [UCT]: 2024-12-29 06:18:18 Age [y:d:h:m:s]: 00:171:14:07:11
Block: 1185536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122348 RingCT/type: yes/0
Extra: 01197aff1c0c3ba4fe06d4b8af06e85293b27affe7788fb09b437c5a20d2551fc2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b989cbef32aafa00c67f9a308ed3c6c3a8eb8e3d4a9fd2d4521e16791977a545 0.600000000000 1672009 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": 1185546, "vin": [ { "gen": { "height": 1185536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b989cbef32aafa00c67f9a308ed3c6c3a8eb8e3d4a9fd2d4521e16791977a545" } } ], "extra": [ 1, 25, 122, 255, 28, 12, 59, 164, 254, 6, 212, 184, 175, 6, 232, 82, 147, 178, 122, 255, 231, 120, 143, 176, 155, 67, 124, 90, 32, 210, 85, 31, 194, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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