Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4155c93f4e0c61636d0e92cc2267bb33167ec7b907aff597e80b4c9ef747ba30

Tx prefix hash: 0f32939a3b8123bc736b10b306d47954a8dfa1da8558366c18ffda1bdcf581d3
Tx public key: 761c763ac0dbc947a01c7ef7e842a90501c9225d85260e2527c081875d5eb4d7
Timestamp: 1761863201 Timestamp [UCT]: 2025-10-30 22:26:41 Age [y:d:h:m:s]: 00:006:20:24:51
Block: 1401511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4886 RingCT/type: yes/0
Extra: 01761c763ac0dbc947a01c7ef7e842a90501c9225d85260e2527c081875d5eb4d7021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 792e5d0e44057fabd8b2a20fc561f8ca7d6e048448d2a9270b6e046b73570d97 0.600000000000 1889830 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": 1401521, "vin": [ { "gen": { "height": 1401511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "792e5d0e44057fabd8b2a20fc561f8ca7d6e048448d2a9270b6e046b73570d97" } } ], "extra": [ 1, 118, 28, 118, 58, 192, 219, 201, 71, 160, 28, 126, 247, 232, 66, 169, 5, 1, 201, 34, 93, 133, 38, 14, 37, 39, 192, 129, 135, 93, 94, 180, 215, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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