Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0096b38be3c20ec243de90eb70d127f469a9437b85484a737d9c947219c1a6c0

Tx prefix hash: 12a17a098a8b91778dbbd5a0e481f9c624db0ca12c8b6826ddf3aac0ca32cbec
Tx public key: b5a8e47df7faea58582ac93bfe229ada40e474e616d7bdae662d8fcec5ad5050
Timestamp: 1704532154 Timestamp [UCT]: 2024-01-06 09:09:14 Age [y:d:h:m:s]: 01:306:19:52:28
Block: 929298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478129 RingCT/type: yes/0
Extra: 01b5a8e47df7faea58582ac93bfe229ada40e474e616d7bdae662d8fcec5ad505002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dde7ea0ff115f67afb29b7970289c9e5f4cd96658d16458e3163a2d5df64a761 0.600000000000 1387170 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": 929308, "vin": [ { "gen": { "height": 929298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dde7ea0ff115f67afb29b7970289c9e5f4cd96658d16458e3163a2d5df64a761" } } ], "extra": [ 1, 181, 168, 228, 125, 247, 250, 234, 88, 88, 42, 201, 59, 254, 34, 154, 218, 64, 228, 116, 230, 22, 215, 189, 174, 102, 45, 143, 206, 197, 173, 80, 80, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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