Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962aac3f9a432749b5aef8eb4368d6b5e68d33696be7c954e8ca2ed877cced4e

Tx prefix hash: f5fb02576a77293df33926bd0fa5baa070a7bf0dce0d40453f1628cf078c3358
Tx public key: 0b41b061be06872e3f25219927fa0929185ed5778bf7640337d22ea808c57077
Timestamp: 1578179223 Timestamp [UCT]: 2020-01-04 23:07:03 Age [y:d:h:m:s]: 05:011:11:11:26
Block: 38845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158262 RingCT/type: yes/0
Extra: 010b41b061be06872e3f25219927fa0929185ed5778bf7640337d22ea808c570770211000000104943cd9f000000000000000000

1 output(s) for total of 456.350708047000 dcy

stealth address amount amount idx
00: 23870f3c93ec49ce61c715b452a4f81551c9df3452fd7541e750dc78c9fa8c0c 456.350708047000 66528 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": 38855, "vin": [ { "gen": { "height": 38845 } } ], "vout": [ { "amount": 456350708047, "target": { "key": "23870f3c93ec49ce61c715b452a4f81551c9df3452fd7541e750dc78c9fa8c0c" } } ], "extra": [ 1, 11, 65, 176, 97, 190, 6, 135, 46, 63, 37, 33, 153, 39, 250, 9, 41, 24, 94, 213, 119, 139, 247, 100, 3, 55, 210, 46, 168, 8, 197, 112, 119, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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