Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fbe352f651e4d5a113f2cd7aaa4c4490f775757431c6bde14a4cb54480c34da

Tx prefix hash: 447abc1b23e316bbbcace32dcb9e8fc564a3edf368e9cbeef2072e10c7129e50
Tx public key: 82f8d868b4c4055c93a599365ccc3441d00e8db396e407d36c99d29dfc1345fc
Timestamp: 1751047340 Timestamp [UCT]: 2025-06-27 18:02:20 Age [y:d:h:m:s]: 00:192:03:58:42
Block: 1314014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135465 RingCT/type: yes/0
Extra: 0182f8d868b4c4055c93a599365ccc3441d00e8db396e407d36c99d29dfc1345fc0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ad44e5c6a60d8201c4a35b9ced3fc511e4b9384fe67234c6f5c4be79c3f7c57 0.600000000000 1801659 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": 1314024, "vin": [ { "gen": { "height": 1314014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ad44e5c6a60d8201c4a35b9ced3fc511e4b9384fe67234c6f5c4be79c3f7c57" } } ], "extra": [ 1, 130, 248, 216, 104, 180, 196, 5, 92, 147, 165, 153, 54, 92, 204, 52, 65, 208, 14, 141, 179, 150, 228, 7, 211, 108, 153, 210, 157, 252, 19, 69, 252, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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