Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ac1366c393a72ead8f06c8ef49abd5813db98b7bfe5e8661a2c3ee99ba4708

Tx prefix hash: 54bcbc148f11fdcd42deb456f6653562cddfbc138044e306e502f732613c9de2
Tx public key: 8cefe235fa35bf3b379b4a1be579d9819c9585bc4ea38d25156e20e2d2e1a7a2
Timestamp: 1708087299 Timestamp [UCT]: 2024-02-16 12:41:39 Age [y:d:h:m:s]: 01:047:13:17:35
Block: 958789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295013 RingCT/type: yes/0
Extra: 018cefe235fa35bf3b379b4a1be579d9819c9585bc4ea38d25156e20e2d2e1a7a202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c939c9fc816a6bcb3ee3a4dd498a71f53de318fff7f96aa4e4fb14878a04b816 0.600000000000 1418150 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": 958799, "vin": [ { "gen": { "height": 958789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c939c9fc816a6bcb3ee3a4dd498a71f53de318fff7f96aa4e4fb14878a04b816" } } ], "extra": [ 1, 140, 239, 226, 53, 250, 53, 191, 59, 55, 155, 74, 27, 229, 121, 217, 129, 156, 149, 133, 188, 78, 163, 141, 37, 21, 110, 32, 226, 210, 225, 167, 162, 2, 17, 0, 0, 0, 2, 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