Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 253e26c8d26e6108d9560f98141ee2363e2193d1603d026b3cf6cfcf807d467f

Tx prefix hash: 02be9f3dbda9945e2fe67872d76c70d95fd90ad6e7be4e69cb194fa6dc9b494b
Tx public key: beefa242e7330d6723e26f7b7dbd0fe9c40ec7d76145733dc01bd4a041bdb381
Timestamp: 1724953822 Timestamp [UCT]: 2024-08-29 17:50:22 Age [y:d:h:m:s]: 00:231:22:45:16
Block: 1098616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165646 RingCT/type: yes/0
Extra: 01beefa242e7330d6723e26f7b7dbd0fe9c40ec7d76145733dc01bd4a041bdb38102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c8487851fa5063d4129f1932ec5679333ee7f2ea3066b97f2e174c8ee71d069 0.600000000000 1574393 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": 1098626, "vin": [ { "gen": { "height": 1098616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c8487851fa5063d4129f1932ec5679333ee7f2ea3066b97f2e174c8ee71d069" } } ], "extra": [ 1, 190, 239, 162, 66, 231, 51, 13, 103, 35, 226, 111, 123, 125, 189, 15, 233, 196, 14, 199, 215, 97, 69, 115, 61, 192, 27, 212, 160, 65, 189, 179, 129, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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