Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e095605943bb9661fa01d770c7f339bf57c9a658becfcc552d94bf1e9cf0452b

Tx prefix hash: b73c1add31d6727a3a07c1cefef892af5405df6f70291e7fad26f5a1bbc4ef7c
Tx public key: 40467c2149f1a3dea2b8e07f6a21f8e8625659ac0b76813f87df26b6400bf9a0
Timestamp: 1736810771 Timestamp [UCT]: 2025-01-13 23:26:11 Age [y:d:h:m:s]: 00:304:12:26:14
Block: 1196779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215147 RingCT/type: yes/0
Extra: 0140467c2149f1a3dea2b8e07f6a21f8e8625659ac0b76813f87df26b6400bf9a0021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e78196b8d7edc889f64325f15a0888bfa0c821599ec88111a7a73ef7d4caaad 0.600000000000 1683382 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": 1196789, "vin": [ { "gen": { "height": 1196779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e78196b8d7edc889f64325f15a0888bfa0c821599ec88111a7a73ef7d4caaad" } } ], "extra": [ 1, 64, 70, 124, 33, 73, 241, 163, 222, 162, 184, 224, 127, 106, 33, 248, 232, 98, 86, 89, 172, 11, 118, 129, 63, 135, 223, 38, 182, 64, 11, 249, 160, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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