Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e115988fefbf856907ddadd537a997b6652d34793a3f99f413b4407e46776e

Tx prefix hash: 72dbe23646a8802d8aca2bc98bcd09206f9161606b363502c75bc6b2b0979e7a
Tx public key: 040f02e9cd5daefcfea4b0662fcd1a5467c3495827a88f306df4c6dbdff362ea
Timestamp: 1726296848 Timestamp [UCT]: 2024-09-14 06:54:08 Age [y:d:h:m:s]: 00:161:21:20:09
Block: 1109754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115497 RingCT/type: yes/0
Extra: 01040f02e9cd5daefcfea4b0662fcd1a5467c3495827a88f306df4c6dbdff362ea021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0f7a022df4c5fcc23bda6b79d3164018dfa78e5fbd921aa51d0819475d61010 0.600000000000 1588121 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": 1109764, "vin": [ { "gen": { "height": 1109754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0f7a022df4c5fcc23bda6b79d3164018dfa78e5fbd921aa51d0819475d61010" } } ], "extra": [ 1, 4, 15, 2, 233, 205, 93, 174, 252, 254, 164, 176, 102, 47, 205, 26, 84, 103, 195, 73, 88, 39, 168, 143, 48, 109, 244, 198, 219, 223, 243, 98, 234, 2, 17, 0, 0, 0, 4, 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