Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f17d65723c0ddfd97714fbd23ca1cb721b45e7fe1a69b132888aea9012bc9391

Tx prefix hash: 0e3993c8e3e117ac7b7e9857fce47705ab887bb345472075c1b7d9295d4a8a00
Tx public key: 907466c576108a1310d1bda571e8dea56b8a1fa3bdaff8de503af17326d7bdfb
Timestamp: 1725106145 Timestamp [UCT]: 2024-08-31 12:09:05 Age [y:d:h:m:s]: 00:229:22:46:28
Block: 1099886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164211 RingCT/type: yes/0
Extra: 01907466c576108a1310d1bda571e8dea56b8a1fa3bdaff8de503af17326d7bdfb021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3e50a2548faf42b855e5e643d4ed306fa596ed046f18da07c971f7f4051c830 0.600000000000 1575855 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": 1099896, "vin": [ { "gen": { "height": 1099886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3e50a2548faf42b855e5e643d4ed306fa596ed046f18da07c971f7f4051c830" } } ], "extra": [ 1, 144, 116, 102, 197, 118, 16, 138, 19, 16, 209, 189, 165, 113, 232, 222, 165, 107, 138, 31, 163, 189, 175, 248, 222, 80, 58, 241, 115, 38, 215, 189, 251, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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