Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b00465824ca6ed124df78d1176cce36d79b52fb4fab4c1441aaf5704baa1efe

Tx prefix hash: 66039541e903947f6273d0ac134c7e8ad24dd8c0d8e8df041171b03212f46e49
Tx public key: c77e49d88a265cd12a472499d50b0449052fe346e91e60c8b4b7636648bec81f
Timestamp: 1577182322 Timestamp [UCT]: 2019-12-24 10:12:02 Age [y:d:h:m:s]: 05:040:07:43:38
Block: 30583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178641 RingCT/type: yes/0
Extra: 01c77e49d88a265cd12a472499d50b0449052fe346e91e60c8b4b7636648bec81f021100000008ad433a0b000000000000000000

1 output(s) for total of 486.034040157000 dcy

stealth address amount amount idx
00: 0df1ba280f94d3255196362b24179252d4eef6504dc9520c3062331b2f2dd962 486.034040157000 50505 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": 30593, "vin": [ { "gen": { "height": 30583 } } ], "vout": [ { "amount": 486034040157, "target": { "key": "0df1ba280f94d3255196362b24179252d4eef6504dc9520c3062331b2f2dd962" } } ], "extra": [ 1, 199, 126, 73, 216, 138, 38, 92, 209, 42, 71, 36, 153, 213, 11, 4, 73, 5, 47, 227, 70, 233, 30, 96, 200, 180, 183, 99, 102, 72, 190, 200, 31, 2, 17, 0, 0, 0, 8, 173, 67, 58, 11, 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