Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 685c7b34aae4986b168ffddb46103a5052260e3d194a2f374f0e05a46d2b3ab3

Tx prefix hash: c4c70bd0fcf524284e13c5092ab1d15c29c7895408428d493c27a8a4e6b2c5f3
Tx public key: c83a57b198085cb16aa85580a85db50e32ab4432fb1308435c269d4cb568e649
Timestamp: 1706393840 Timestamp [UCT]: 2024-01-27 22:17:20 Age [y:d:h:m:s]: 01:283:16:19:46
Block: 944728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461532 RingCT/type: yes/0
Extra: 01c83a57b198085cb16aa85580a85db50e32ab4432fb1308435c269d4cb568e64902110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dda0ccc40d3c17d9f4cd7361224d9c53dd086b4cc2c48adb4662a764a90d989 0.600000000000 1403014 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": 944738, "vin": [ { "gen": { "height": 944728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dda0ccc40d3c17d9f4cd7361224d9c53dd086b4cc2c48adb4662a764a90d989" } } ], "extra": [ 1, 200, 58, 87, 177, 152, 8, 92, 177, 106, 168, 85, 128, 168, 93, 181, 14, 50, 171, 68, 50, 251, 19, 8, 67, 92, 38, 157, 76, 181, 104, 230, 73, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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