Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e19873139de701f2ac1211e8113d53114ba411a8c5fd4f10801a0479c9fcc625

Tx prefix hash: 6d44b5a85783fb3e24cf265da504b3be56659aee6e398d8a7b5d054b43246cbb
Tx public key: bd94878cfa41d3308163b4ab70efc8a5d9f5fbb153fcc6993b6b29d270a03d16
Timestamp: 1736244296 Timestamp [UCT]: 2025-01-07 10:04:56 Age [y:d:h:m:s]: 00:164:09:37:31
Block: 1192093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117164 RingCT/type: yes/0
Extra: 01bd94878cfa41d3308163b4ab70efc8a5d9f5fbb153fcc6993b6b29d270a03d16021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac4e58ccc0d78d006df76d2438174d45de0334ffc2c7a0a1547c536b8457f85 0.600000000000 1678638 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": 1192103, "vin": [ { "gen": { "height": 1192093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac4e58ccc0d78d006df76d2438174d45de0334ffc2c7a0a1547c536b8457f85" } } ], "extra": [ 1, 189, 148, 135, 140, 250, 65, 211, 48, 129, 99, 180, 171, 112, 239, 200, 165, 217, 245, 251, 177, 83, 252, 198, 153, 59, 107, 41, 210, 112, 160, 61, 22, 2, 17, 0, 0, 0, 5, 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