Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 079add0dcc19d4b5e633893a41f5bdcca6f3db644d625fe0c21c7a2b08f1ef33

Tx prefix hash: 2185a82b43dec63175d7ed29d769f831400752c23de0a35a04104672f051b752
Tx public key: 831a2e2cc9f6a35ae150a1ed78af9cc911befbfdcb2710cf4a333ff0ea13faff
Timestamp: 1731261619 Timestamp [UCT]: 2024-11-10 18:00:19 Age [y:d:h:m:s]: 00:013:20:09:58
Block: 1150834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9904 RingCT/type: yes/0
Extra: 01831a2e2cc9f6a35ae150a1ed78af9cc911befbfdcb2710cf4a333ff0ea13faff0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536897bcab06e665274cd4db749bbf0e3c8e264421ae0691440df130d84f8e00 0.600000000000 1636245 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": 1150844, "vin": [ { "gen": { "height": 1150834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536897bcab06e665274cd4db749bbf0e3c8e264421ae0691440df130d84f8e00" } } ], "extra": [ 1, 131, 26, 46, 44, 201, 246, 163, 90, 225, 80, 161, 237, 120, 175, 156, 201, 17, 190, 251, 253, 203, 39, 16, 207, 74, 51, 63, 240, 234, 19, 250, 255, 2, 17, 0, 0, 0, 1, 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