Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ec21c855ddcc0f415ca6e8b515ac058c42bd7de2116463713b0161edfd206aa

Tx prefix hash: 025796c960fde6a201bcfe910d58a38b281e98a607368fc9f5c1c2619f32e2b7
Tx public key: f871d610c18ac52bb2d937fd2573007c99e45b92d9590e995b7079bfcc3e4e65
Timestamp: 1712727707 Timestamp [UCT]: 2024-04-10 05:41:47 Age [y:d:h:m:s]: 01:028:23:19:50
Block: 997238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281693 RingCT/type: yes/0
Extra: 01f871d610c18ac52bb2d937fd2573007c99e45b92d9590e995b7079bfcc3e4e65021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3614a04916a75421a2ab070530a1fa51dffcf08f87087043d6565bbd3d6d895 0.600000000000 1457668 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": 997248, "vin": [ { "gen": { "height": 997238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3614a04916a75421a2ab070530a1fa51dffcf08f87087043d6565bbd3d6d895" } } ], "extra": [ 1, 248, 113, 214, 16, 193, 138, 197, 43, 178, 217, 55, 253, 37, 115, 0, 124, 153, 228, 91, 146, 217, 89, 14, 153, 91, 112, 121, 191, 204, 62, 78, 101, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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