Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb16847a7620fabf948ea415368c9295687ae820ea56a9d7e942d65f0c17aca7

Tx prefix hash: df753a9a292c95685a1674321473eabc107809e3d6541c2e305e15398e26c0eb
Tx public key: 9fed5d47b6f4c8db101721a026a63273714e3f5bba9c0bc1b0a514072663168d
Timestamp: 1745494111 Timestamp [UCT]: 2025-04-24 11:28:31 Age [y:d:h:m:s]: 00:210:16:49:33
Block: 1268406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148291 RingCT/type: yes/0
Extra: 019fed5d47b6f4c8db101721a026a63273714e3f5bba9c0bc1b0a514072663168d021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4163edc060df6c9a387a798b967571cfd2957c4cad8d22727ada487331db09f3 0.600000000000 1755635 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": 1268416, "vin": [ { "gen": { "height": 1268406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4163edc060df6c9a387a798b967571cfd2957c4cad8d22727ada487331db09f3" } } ], "extra": [ 1, 159, 237, 93, 71, 182, 244, 200, 219, 16, 23, 33, 160, 38, 166, 50, 115, 113, 78, 63, 91, 186, 156, 11, 193, 176, 165, 20, 7, 38, 99, 22, 141, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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