Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04b255a5e0889f7815198622dd0290b1735fe92b76781c2a86c3e94a8b1e113a

Tx prefix hash: 2e8cd522bca1b4b9cc38c5d3240b841c216fa849b496c64b4a0f55ab2d1916a8
Tx public key: 7008618c0ee62102df20e1e1ac6ee28410096d5817ec43b2b7112a1f1e745868
Timestamp: 1706995202 Timestamp [UCT]: 2024-02-03 21:20:02 Age [y:d:h:m:s]: 00:341:15:28:41
Block: 949720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244596 RingCT/type: yes/0
Extra: 017008618c0ee62102df20e1e1ac6ee28410096d5817ec43b2b7112a1f1e7458680211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9615f835bb5f47e8c787567de29f2bf85f18ff3a704357c3b984fa5c43ec1513 0.600000000000 1408252 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": 949730, "vin": [ { "gen": { "height": 949720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9615f835bb5f47e8c787567de29f2bf85f18ff3a704357c3b984fa5c43ec1513" } } ], "extra": [ 1, 112, 8, 97, 140, 14, 230, 33, 2, 223, 32, 225, 225, 172, 110, 226, 132, 16, 9, 109, 88, 23, 236, 67, 178, 183, 17, 42, 31, 30, 116, 88, 104, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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