Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e70e026c2d68bd084eb8222e576199f9811c338bbccf26b09ad02fb2c30ead36

Tx prefix hash: 51cc4a0595a61072817034f9ea512fba7604738eb7ca90f370cc1c910f1bb68f
Tx public key: 0927bda45d9f284361f9b291a736c79d5d6f52cd821846e7e73784b109a6dbc9
Timestamp: 1685448202 Timestamp [UCT]: 2023-05-30 12:03:22 Age [y:d:h:m:s]: 02:158:14:54:22
Block: 771358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 633141 RingCT/type: yes/0
Extra: 010927bda45d9f284361f9b291a736c79d5d6f52cd821846e7e73784b109a6dbc9021100000001faf35c9c000000000000000000

1 output(s) for total of 1.706753931000 dcy

stealth address amount amount idx
00: 729e3fd1cebcb206636bd877984d6495e68d07301202e570e8a61771525deeb3 1.706753931000 1220713 of 0

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": 771368, "vin": [ { "gen": { "height": 771358 } } ], "vout": [ { "amount": 1706753931, "target": { "key": "729e3fd1cebcb206636bd877984d6495e68d07301202e570e8a61771525deeb3" } } ], "extra": [ 1, 9, 39, 189, 164, 93, 159, 40, 67, 97, 249, 178, 145, 167, 54, 199, 157, 93, 111, 82, 205, 130, 24, 70, 231, 231, 55, 132, 177, 9, 166, 219, 201, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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