Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00815f025f6e4d50f17ef65637752272f0b3a73ac4a8087ab1f4279589e0acfd

Tx prefix hash: eded80c271164efe39c9673aa9a3b082b0d90a5f70638dfdd1cba0aaa2082eed
Tx public key: ee47ead76bdd07bdd19041fa9c35f9d52ed90eb25ae4ab9e0d40aea97784c13b
Timestamp: 1704670660 Timestamp [UCT]: 2024-01-07 23:37:40 Age [y:d:h:m:s]: 01:049:23:37:53
Block: 930451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296804 RingCT/type: yes/0
Extra: 01ee47ead76bdd07bdd19041fa9c35f9d52ed90eb25ae4ab9e0d40aea97784c13b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66eede7455193a29d60cb9472b8add442677b1cb7d9e8eeabb2c8cb4ad024583 0.600000000000 1388333 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": 930461, "vin": [ { "gen": { "height": 930451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66eede7455193a29d60cb9472b8add442677b1cb7d9e8eeabb2c8cb4ad024583" } } ], "extra": [ 1, 238, 71, 234, 215, 107, 221, 7, 189, 209, 144, 65, 250, 156, 53, 249, 213, 46, 217, 14, 178, 90, 228, 171, 158, 13, 64, 174, 169, 119, 132, 193, 59, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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