Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 739f783059da3eef1815285d19cb7bcf6c20a5967e43507625ba9a53ef6dc43f

Tx prefix hash: 7a4f9861347bec6c5e78238ee60a54f7d83a53bb314ed3cfea55f7539f468629
Tx public key: 01634a12e366299fba5b20ea6609928e40a0212cd10d0b9d68d90df079512418
Timestamp: 1707632486 Timestamp [UCT]: 2024-02-11 06:21:26 Age [y:d:h:m:s]: 01:073:10:19:27
Block: 955015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313543 RingCT/type: yes/0
Extra: 0101634a12e366299fba5b20ea6609928e40a0212cd10d0b9d68d90df0795124180211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf567d3b6285a046967051e011cc55d5efb89b0c5161b1d7a57b8b4aa8aba57 0.600000000000 1414297 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": 955025, "vin": [ { "gen": { "height": 955015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf567d3b6285a046967051e011cc55d5efb89b0c5161b1d7a57b8b4aa8aba57" } } ], "extra": [ 1, 1, 99, 74, 18, 227, 102, 41, 159, 186, 91, 32, 234, 102, 9, 146, 142, 64, 160, 33, 44, 209, 13, 11, 157, 104, 217, 13, 240, 121, 81, 36, 24, 2, 17, 0, 0, 0, 4, 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