Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12bbe92c6ab696e3b4b8e0ebdcfc5c459adacaf19c5f836fcb5eb85f7bb194c3

Tx prefix hash: a0e6edd8dbaf61317ccba58ca3df53682eb19dd2bc2e894f3b3fbdf489de9d4f
Tx public key: de18d05580b572ff61c133c72f9853a0b5fcdcf5fdc699fbb1647a435c66deb1
Timestamp: 1657771251 Timestamp [UCT]: 2022-07-14 04:00:51 Age [y:d:h:m:s]: 02:173:12:21:55
Block: 543337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645366 RingCT/type: yes/0
Extra: 01de18d05580b572ff61c133c72f9853a0b5fcdcf5fdc699fbb1647a435c66deb10211000000015eb576c5000000000000000000

1 output(s) for total of 9.720735163000 dcy

stealth address amount amount idx
00: 7b0a6245a68ba0b35d1d0d3b1a5c84815e380c82a719063342d18739d2793af2 9.720735163000 973996 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": 543347, "vin": [ { "gen": { "height": 543337 } } ], "vout": [ { "amount": 9720735163, "target": { "key": "7b0a6245a68ba0b35d1d0d3b1a5c84815e380c82a719063342d18739d2793af2" } } ], "extra": [ 1, 222, 24, 208, 85, 128, 181, 114, 255, 97, 193, 51, 199, 47, 152, 83, 160, 181, 252, 220, 245, 253, 198, 153, 251, 177, 100, 122, 67, 92, 102, 222, 177, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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