Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3898b1eede64075b41919b3d7e8564c2f5eaf102584c2972592152076bf7fa6f

Tx prefix hash: cc8e9690ff49be1e5aa74be828fa9c824d2d1932234bc834aefc0c6e25480c10
Tx public key: 3b9ee23750df7696c72263207bb7490b16a401c40a14d4e8698d8fd0c47dfc0d
Timestamp: 1756228482 Timestamp [UCT]: 2025-08-26 17:14:42 Age [y:d:h:m:s]: 00:119:15:18:40
Block: 1354987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85471 RingCT/type: yes/0
Extra: 013b9ee23750df7696c72263207bb7490b16a401c40a14d4e8698d8fd0c47dfc0d0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa9feab47985823f16ef0bf3dfaa65ba551b1fab97f72b7bbc01ba0b79e7325e 0.600000000000 1842982 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": 1354997, "vin": [ { "gen": { "height": 1354987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa9feab47985823f16ef0bf3dfaa65ba551b1fab97f72b7bbc01ba0b79e7325e" } } ], "extra": [ 1, 59, 158, 226, 55, 80, 223, 118, 150, 199, 34, 99, 32, 123, 183, 73, 11, 22, 164, 1, 196, 10, 20, 212, 232, 105, 141, 143, 208, 196, 125, 252, 13, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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