Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde93d52c9f0ace948593d053aef2a6b649be380edc2a8e2bb8f46c135f01852

Tx prefix hash: 00620c24bc9cc3098c9c30a075bc0f67d6be421e08fe444b63417807db920496
Tx public key: ea380cd760efbfb595d4ee38d58e2638b53d80db9f511b3f990c9a8b51912fbe
Timestamp: 1734584733 Timestamp [UCT]: 2024-12-19 05:05:33 Age [y:d:h:m:s]: 00:103:09:04:00
Block: 1178379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73643 RingCT/type: yes/0
Extra: 01ea380cd760efbfb595d4ee38d58e2638b53d80db9f511b3f990c9a8b51912fbe02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e8bf4194fd582683bfd7ba8c296a158cf1f7a1ef407b24bb2caf30262b67269 0.600000000000 1664766 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": 1178389, "vin": [ { "gen": { "height": 1178379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e8bf4194fd582683bfd7ba8c296a158cf1f7a1ef407b24bb2caf30262b67269" } } ], "extra": [ 1, 234, 56, 12, 215, 96, 239, 191, 181, 149, 212, 238, 56, 213, 142, 38, 56, 181, 61, 128, 219, 159, 81, 27, 63, 153, 12, 154, 139, 81, 145, 47, 190, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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