Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c723cf1dcb5041624eb5999dc104c0ddb3c846244b0568a87c62409ad56ec4f

Tx prefix hash: 6716898e6a021c25e419a311703e795aefba7ced2498d014b7aafce4ce974ab1
Tx public key: 65b76f08b6c5e9d39998747a39f87771f21d6e957ff225855b575745794c0cdd
Timestamp: 1631408584 Timestamp [UCT]: 2021-09-12 01:03:04 Age [y:d:h:m:s]: 03:145:05:10:13
Block: 331968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879043 RingCT/type: yes/0
Extra: 0165b76f08b6c5e9d39998747a39f87771f21d6e957ff225855b575745794c0cdd021100000031a272b9cb000000000000000000

1 output(s) for total of 48.760460088000 dcy

stealth address amount amount idx
00: 97a7eb84d37571c130dc7374b35242d0c4c6313770936843e83468dccb74a7cb 48.760460088000 685739 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": 331978, "vin": [ { "gen": { "height": 331968 } } ], "vout": [ { "amount": 48760460088, "target": { "key": "97a7eb84d37571c130dc7374b35242d0c4c6313770936843e83468dccb74a7cb" } } ], "extra": [ 1, 101, 183, 111, 8, 182, 197, 233, 211, 153, 152, 116, 122, 57, 248, 119, 113, 242, 29, 110, 149, 127, 242, 37, 133, 91, 87, 87, 69, 121, 76, 12, 221, 2, 17, 0, 0, 0, 49, 162, 114, 185, 203, 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