Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a64de6ede403bfdcc05019d90544540f82d5b55ce1fd9e7485207edc7e58836

Tx prefix hash: 94f2b1c8f8e4dc046e03d179c37e64a0edf15dbde8bac01ef009748fb567584b
Tx public key: 02cd489164ed8767a01e6d6ea3091a1eae41eeede7ab5525a7ca80f730c19e79
Timestamp: 1710699518 Timestamp [UCT]: 2024-03-17 18:18:38 Age [y:d:h:m:s]: 00:342:12:59:06
Block: 980471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244863 RingCT/type: yes/0
Extra: 0102cd489164ed8767a01e6d6ea3091a1eae41eeede7ab5525a7ca80f730c19e7902110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f98ff8f30aebbfb8881a97c3bff129e21dd3694f504dea0e7fe1cc8f200eb76 0.600000000000 1440538 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": 980481, "vin": [ { "gen": { "height": 980471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f98ff8f30aebbfb8881a97c3bff129e21dd3694f504dea0e7fe1cc8f200eb76" } } ], "extra": [ 1, 2, 205, 72, 145, 100, 237, 135, 103, 160, 30, 109, 110, 163, 9, 26, 30, 174, 65, 238, 237, 231, 171, 85, 37, 167, 202, 128, 247, 48, 193, 158, 121, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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