Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 095b671474138e9dcf5a7064889bb76bfd7e31e71d160974961c496ec258ada0

Tx prefix hash: 9e11cc4a3676715ee43ed55b0e165f9bcba41d44e47b16e7fe7a8a29f85b4fd0
Tx public key: 5a78c21ce08e24e8c2adb3dda40fd1f8a171e7927cff1be66840a7072585a04c
Timestamp: 1708622633 Timestamp [UCT]: 2024-02-22 17:23:53 Age [y:d:h:m:s]: 01:032:10:38:09
Block: 963232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284189 RingCT/type: yes/0
Extra: 015a78c21ce08e24e8c2adb3dda40fd1f8a171e7927cff1be66840a7072585a04c02110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c65e75e37eb23e5cbe7a0c17ec35c94e93f2ce300466867dac98d4a0fd1899e 0.600000000000 1422933 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": 963242, "vin": [ { "gen": { "height": 963232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c65e75e37eb23e5cbe7a0c17ec35c94e93f2ce300466867dac98d4a0fd1899e" } } ], "extra": [ 1, 90, 120, 194, 28, 224, 142, 36, 232, 194, 173, 179, 221, 164, 15, 209, 248, 161, 113, 231, 146, 124, 255, 27, 230, 104, 64, 167, 7, 37, 133, 160, 76, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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