Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a1b9f2ba85d196bc8aa37d4c60a7f820e4aa3307731513a626a459363bd296d

Tx prefix hash: 988c06b4b30f6dda7287601c8400c7c1d1ff9de17a51cc50ad97abb691005cf6
Tx public key: e21d8ea9bb39eb3003531d75fb6991f2d382ffaa16dd79a914fe62f7f9bd517e
Timestamp: 1736181176 Timestamp [UCT]: 2025-01-06 16:32:56 Age [y:d:h:m:s]: 00:156:21:29:45
Block: 1191583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111912 RingCT/type: yes/0
Extra: 01e21d8ea9bb39eb3003531d75fb6991f2d382ffaa16dd79a914fe62f7f9bd517e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 663500a8cce98d08caf564b92062603fa33fbf8cbb2af9184cbb4efb9f14d08c 0.600000000000 1678122 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": 1191593, "vin": [ { "gen": { "height": 1191583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "663500a8cce98d08caf564b92062603fa33fbf8cbb2af9184cbb4efb9f14d08c" } } ], "extra": [ 1, 226, 29, 142, 169, 187, 57, 235, 48, 3, 83, 29, 117, 251, 105, 145, 242, 211, 130, 255, 170, 22, 221, 121, 169, 20, 254, 98, 247, 249, 189, 81, 126, 2, 17, 0, 0, 0, 2, 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