Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9d86a737349855c63869c05ea3ed430df9b24fbf402bfa20da46ab26e034195

Tx prefix hash: 08145b63cffe375b76391e6454911aaaf432b7480e18f98d3149aece3912ece7
Tx public key: 26e907a7b7ee49c8ed2f6b02ee3d79f05b307332041e097e5353551ff20b0dd9
Timestamp: 1721133764 Timestamp [UCT]: 2024-07-16 12:42:44 Age [y:d:h:m:s]: 00:245:21:55:49
Block: 1066979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175669 RingCT/type: yes/0
Extra: 0126e907a7b7ee49c8ed2f6b02ee3d79f05b307332041e097e5353551ff20b0dd902110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e107d93a91e6ffd5c8df4b02db74928b85e6caafc12d7e3f79ff860dac9b76b2 0.600000000000 1537668 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": 1066989, "vin": [ { "gen": { "height": 1066979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e107d93a91e6ffd5c8df4b02db74928b85e6caafc12d7e3f79ff860dac9b76b2" } } ], "extra": [ 1, 38, 233, 7, 167, 183, 238, 73, 200, 237, 47, 107, 2, 238, 61, 121, 240, 91, 48, 115, 50, 4, 30, 9, 126, 83, 83, 85, 31, 242, 11, 13, 217, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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