Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3d9ecfdb621f8026dd2969f2b3f303f5fe5d5f2d18580275bc821bcd571ae7

Tx prefix hash: edc43814fd997e91d35194c837d8fb61c026e195d19ee8d66e5a23f653e22eb0
Tx public key: 5e622a87c8ea33007004832314d571f8ce9915b9bbb2682134d0a4dce89d0fd8
Timestamp: 1698225580 Timestamp [UCT]: 2023-10-25 09:19:40 Age [y:d:h:m:s]: 01:193:08:47:54
Block: 877247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399220 RingCT/type: yes/0
Extra: 015e622a87c8ea33007004832314d571f8ce9915b9bbb2682134d0a4dce89d0fd8021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.760880656000 dcy

stealth address amount amount idx
00: 3a365c61cedee026e9e2c92b85ee8c5764a88e7e21f63c995fe5bd10a4f1d807 0.760880656000 1332615 of 0

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": 877257, "vin": [ { "gen": { "height": 877247 } } ], "vout": [ { "amount": 760880656, "target": { "key": "3a365c61cedee026e9e2c92b85ee8c5764a88e7e21f63c995fe5bd10a4f1d807" } } ], "extra": [ 1, 94, 98, 42, 135, 200, 234, 51, 0, 112, 4, 131, 35, 20, 213, 113, 248, 206, 153, 21, 185, 187, 178, 104, 33, 52, 208, 164, 220, 232, 157, 15, 216, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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