Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f794fc48bc683e7df34c81b1c886aa0a35b5fc32692fcf8ccfb22f36c4b1169

Tx prefix hash: 89eac002c8c143af59c1a07206e7cf069fac074ef1bed25ae75c903ff29913a6
Tx public key: 4b6cec8fe42ce8fdda1645676eb49d62660bd6e66315f339fe5f7b76a7d77e2d
Timestamp: 1751224537 Timestamp [UCT]: 2025-06-29 19:15:37 Age [y:d:h:m:s]: 00:137:12:03:06
Block: 1315349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96449 RingCT/type: yes/0
Extra: 014b6cec8fe42ce8fdda1645676eb49d62660bd6e66315f339fe5f7b76a7d77e2d021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee4814f47614edf1de2647652e293b2caf067f24e1174391e9e4df7c16a626f 0.600000000000 1803004 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": 1315359, "vin": [ { "gen": { "height": 1315349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee4814f47614edf1de2647652e293b2caf067f24e1174391e9e4df7c16a626f" } } ], "extra": [ 1, 75, 108, 236, 143, 228, 44, 232, 253, 218, 22, 69, 103, 110, 180, 157, 98, 102, 11, 214, 230, 99, 21, 243, 57, 254, 95, 123, 118, 167, 215, 126, 45, 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