Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b007dea7e3082bd956a2467c5d3c2450fa658ff88f8a4bdb61f14b1d1c98716

Tx prefix hash: d5fc4ea8d80692fb32a8953bb8e7da475806d1bd00763b78337c79eb85728e03
Tx public key: 556a27794475842bd380981b6c28f00a1be6ab3c3df059310ca9ee6abdbebe90
Timestamp: 1676479575 Timestamp [UCT]: 2023-02-15 16:46:15 Age [y:d:h:m:s]: 02:061:12:48:02
Block: 697636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565570 RingCT/type: yes/0
Extra: 01556a27794475842bd380981b6c28f00a1be6ab3c3df059310ca9ee6abdbebe9002110000000174b6d784000000000000000000

1 output(s) for total of 2.995313241000 dcy

stealth address amount amount idx
00: 3f9f52bb4caa7eba8b6a548dbdd1baa57f627659993c8ff8fed4cf923c3f8125 2.995313241000 1140879 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": 697646, "vin": [ { "gen": { "height": 697636 } } ], "vout": [ { "amount": 2995313241, "target": { "key": "3f9f52bb4caa7eba8b6a548dbdd1baa57f627659993c8ff8fed4cf923c3f8125" } } ], "extra": [ 1, 85, 106, 39, 121, 68, 117, 132, 43, 211, 128, 152, 27, 108, 40, 240, 10, 27, 230, 171, 60, 61, 240, 89, 49, 12, 169, 238, 106, 189, 190, 190, 144, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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