Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28be62c17ef156daf93f7369efa0bb8fd4d8c9d560745c7702a25a4c48789c65

Tx prefix hash: 8496511b534bdd5ea2ff8dfba7b6dd6368f81303c8f741255988259f9e1be98b
Tx public key: 954b8b974dab560d9a4e253c92e68c166bb0c4f736541ecdc105b3cad10b75e4
Timestamp: 1761043999 Timestamp [UCT]: 2025-10-21 10:53:19 Age [y:d:h:m:s]: 00:062:20:04:57
Block: 1394719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44976 RingCT/type: yes/0
Extra: 01954b8b974dab560d9a4e253c92e68c166bb0c4f736541ecdc105b3cad10b75e402110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a05f159b7599a337a321f811e99bf49957fe557951c14c5ccab8d33a18e9885a 0.600000000000 1882994 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": 1394729, "vin": [ { "gen": { "height": 1394719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a05f159b7599a337a321f811e99bf49957fe557951c14c5ccab8d33a18e9885a" } } ], "extra": [ 1, 149, 75, 139, 151, 77, 171, 86, 13, 154, 78, 37, 60, 146, 230, 140, 22, 107, 176, 196, 247, 54, 84, 30, 205, 193, 5, 179, 202, 209, 11, 117, 228, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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